Build, test, and submit your app using Xcode, Apple's integrated development environment.

Posts under Xcode tag

200 Posts

Post

Replies

Boosts

Views

Activity

Resolving a "Simulator runtime is not available" error
Some Macs recently received a macOS system update which disabled the simulator runtimes used by Xcode 15, including the simulators for iOS, tvOS, watchOS, and visionOS. If your Mac received this update, you will receive the following error message and will be unable to use the simulator: The com.apple.CoreSimulator.SimRuntime.iOS-17-2 simulator runtime is not available. Domain: com.apple.CoreSimulator.SimError Code: 401 Failure Reason: runtime profile not found using "System" match policy Recovery Suggestion: Download the com.apple.CoreSimulator.SimRuntime.iOS-17-2 simulator runtime from the Xcode To resume using the simulator, please reboot your Mac. After rebooting, check Xcode Preferences → Platforms to ensure that the simulator runtime you would like to use is still installed. If it is missing, use the Get button to download it again. The Xcode 15.3 Release Notes are also updated with this information.
0
0
11k
May ’24
Questions about swift student challenge 27
I'm excited to see the announcement of Swift Student Challenge 27, but I have a couple of questions: The rules mention that Xcode Apps are allowed. Does this mean we can create and submit a folder containing an .xcodeproj file instead of a .swiftpm Swift Playgrounds package? While it's great to see support across all Apple platforms this year, I'm a bit concerned about whether the judges will test submissions on physical devices or in the simulator. I had a similar concern last year (https://developer.apple.com/forums/thread/812429). Thanks!
2
0
177
4h
Supported way to supervise an iOS Simulator XCTest host before application code executes?
We are investigating a supported architecture for running existing app-hosted XCTest unit and integration tests in iOS Simulator under external process supervision. Our environment is Xcode 27.2, targeting ARM64 iOS Simulator. The tests use SwiftData, CoreData and SQLite with synthetic, test-owned databases. We need to run selected tests serially in isolated processes, monitor their resource usage, and verify that all test-related processes have terminated before cleaning up test databases. Our primary question: Is there a documented, supported way to establish external process supervision before the actual iOS Simulator XCTest host executes any application or test-bundle code? In particular, we are looking for guidance on the following: Pre-execution control: Can the actual XCTest host be launched suspended and released only after an external supervisor has established monitoring? We need coverage of application and test-bundle initialization, not merely a callback before the first test method. Process identity: Is there a supported mechanism to identify and monitor the actual host process using an OS-verifiable identity that remains reliable despite PID reuse? Process termination: Is there a supported way to identify and terminate only the processes belonging to a specific test run, including detached or reparented children, without affecting unrelated Simulator processes? XCTest integration: Can this be achieved while preserving normal XCTest discovery, setup/teardown, asynchronous tests and genuine .xcresult reporting? We have investigated public XCTest APIs, standard xcodebuild workflows and macOS process-control mechanisms. We also successfully compiled and linked a separate ARM64 Simulator executable against our unchanged application debug dylib and XCTest dependencies. However, this was strictly a compile/link experiment: the executable was never launched, and we have not established that a custom XCTest host is supported. We are not seeking private APIs or undocumented CoreSimulator behavior. If this level of supervision is not supported, what is Apple’s recommended documented alternative? In particular, does the standard Xcode-managed XCTest workflow provide any documented guarantees regarding host process identity, lifecycle containment and complete termination of test-related processes? References to official documentation or supported examples would be greatly appreciated.
0
0
26
1d
Apple Watch SE 3 fails to pair with Xcode Device Hub: protocol_shoes does not support endpoint type 3
Hi all, I cannot pair a physical Apple Watch SE 3 with Xcode, and I would like to know if anyone else sees this or has found a workaround. Environment Apple Watch SE 3 (GPS, Watch7,13), watchOS 27.2.1 (24S132) Companion iPhone 15 Plus, iOS 27.2 (24B119) Tested on two different Macs: a MacBook Air (macOS 27.2.1, Xcode 27.2) and an iMac Developer Mode is enabled on both the iPhone and the Watch The iPhone is trusted, connects to the Mac, and appears in Device Hub Problem The Watch shows “Pair with <Mac name>” in its Developer Mode settings. When I tap it, pairing does not complete and the Watch does not appear in Device Hub. Watch log (remotepairingdeviced). The sysdiagnose shows the pairing request failing within about 20 ms. Log prefixes and the endpoint address are omitted: Received request to wirelessly pair from peer Path is satisfied; interface: ipsec2; uses wifi, proxy Endpoint type is not an address or host, cannot synthesize URL protocol_shoes does not support endpoint type 3 Failed to attach application protocol shoes Received pairing outcome failure (errorCode: -1, "An unknown error occurred.")What I tried Restarted the Watch, iPhone and Mac Tested on two Macs and on different Wi-Fi networks Turning Bluetooth off on the iPhone: the Watch then no longer discovers the Mac at all The same failure appears in the Watch sysdiagnoses for all attempts. I filed a report in Feedback Assistant: FB25623613 Has anyone seen this error or found a workaround? Thanks
0
0
48
1d
Accessibility Inspector Element Detection and contrast failures with SwiftUI sheets
I am investigating Accessibility Inspector/XCTest audit results in a SwiftUI app (Target Keeper), without suppressing warnings. Environment: Xcode 27.1 (27A9275), iPadOS 27.0 Simulator, macOS 27.0.1. Debug and Release builds pass. The app uses scalable text and labeled controls. Element Detection / native sheet Main-screen Element Detection passes when the sheet is closed. With a SwiftUI .sheet presented, the iPad audit reports “Potentially inaccessible text”; XCUIAccessibilityAuditIssue.element is nil. Exported Inspector HTML highlights background labels behind/outside the sheet, rather than a foreground control. The separate, data-free SwiftUI application below reproduces the modal-only warning; it links no application modules or persistence. Actual iPad Simulator VoiceOver testing using XCUIDevice.shared.voiceOverService passes forward/backward traversal of the real application's modal controls, without reaching the background labels. This is simulator evidence, not physical-device acceptance. A trial explicit modal container/.isModal trait did not clear the audit and was reverted; no warnings are filtered. Minimal independent app: import SwiftUI @main struct ModalRepro: App { @State private var showing=false private let names=["Vegetables","Protein","Fruit","Dairy","Grains","Healthy Fats"] var body:some Scene {WindowGroup { NavigationStack { VStack(spacing:24) { Button("Nutrition") {}.accessibilityLabel("Choose Page").accessibilityValue("Nutrition") LazyVGrid(columns:[GridItem(.flexible()),GridItem(.flexible()),GridItem(.flexible())],spacing:40) { ForEach(names,id:\.self) { name in Button {} label: { VStack(spacing:10) { Circle().fill(.blue.opacity(0.3)).frame(width:250,height:250) Text(name).font(.system(size:17)).accessibilityHidden(true) } }.buttonStyle(.plain).accessibilityLabel(name) } } Button("Show modal") {showing=true} }.padding(24).frame(maxWidth:.infinity,maxHeight:.infinity).background(Color.black) }.preferredColorScheme(.dark) .sheet(isPresented:$showing) { NavigationStack { VStack {Text("Foreground content");Button("Close") {showing=false}} .frame(maxWidth:.infinity,maxHeight:.infinity).background(Color.black) .navigationTitle("Modal flow") }.preferredColorScheme(.dark) } }} }In an Xcode UI-test target, launch this app, run try app.performAccessibilityAudit(for: [.elementDetection]), tap “Show modal”, then run the same audit again. The first passes and the second fails. No issue handler ignores failures. Contrast / scrolling — separate unresolved finding All four iPhone combined-audit configurations (portrait/landscape, normal/maximum Dynamic Type) pass in the tested picker state. However, iPad maximum-text combined audits and a separate scrolled iPhone maximum-text landscape contrast audit still fail; we are not calling these resolved. In the scrolled iPhone case, XCTest identifies a count label whose frame is entirely above the visible results viewport. Inspector's exported HTML reports 1.37:1 using #252526 versus #000000; its marked screenshot rectangle overlaps the dark search/header area, not visible count text. Visible sampled labels instead have white or light foregrounds on opaque dark fills (e.g. #FFFFFF/#1C1C1E = 17.01:1; #98989F/#1C1C1E = 5.94:1). These are screenshot core-pixel measurements, not proof every warning is false. We compare ordinary text against 4.5:1 and interactive non-text against 3:1. iPad maximum-text warnings have not yet been matched to an exact visible color pair. Original failures and HTML exports are preserved privately. Questions Is Element Detection expected to inspect background elements behind a presented native SwiftUI sheet? Is this a known tool limitation/framework issue, or does the sample need different semantics? What is the supported way to establish modal accessibility boundaries with SwiftUI sheets, and when should .isModal be added explicitly? How should we distinguish a real contrast defect from clipping, occlusion, translucency, or sampling of an offscreen element? Which Inspector export fields/diagnostics should establish the actual sampled text/background pair? What additional evidence/manual and physical-device tests does Apple recommend before qualifying accessibility when the minimal audit reproduction fails but actual VoiceOver modal focus behaves correctly? We are not asking to waive audits or declare full accessibility from a VoiceOver pass alone. I read Apple's audit guidance and modal trait documentation: https://developer.apple.com/documentation/accessibility/performing-accessibility-audits-for-your-app https://developer.apple.com/documentation/swiftui/accessibilitytraits/ismodal https://developer.apple.com/help/app-store-connect/manage-app-accessibility/sufficient-contrast-evaluation-criteria/ Related discussion https://developer.apple.com/forums/thread/823968 recommends Feedback for a different apparent Dynamic Type false positive; it does not answer these modal/contrast questions. A Feedback draft is prepared but not submitted, so I have no Feedback ID yet. No private data, identifiers, credentials, app containers or confidential application source are included.
2
0
1.2k
1d
Documentation in Xcode not downloading
Switched to Xcode 27.2 and it started downloading documentation. After download is finished documentation window is empty, prompting to look up documenation online or download it. Triggering any download does not help – no documentation is available. (Sidenote: Reinstalled Xcode 27.2 and documentation was there. But Xcode started a download automatically and without confirmation and afterwards it is gone)
2
2
94
1d
Xcode 27 and Intel Macs: Let's Make Our Voices Heard
I would like to express my disappointment with Apple's decision to drop Intel Mac support in Xcode 27, and I believe we should speak up about it. I'm still using my 27-inch Retina 5K iMac from 2020, with a 3.3 GHz 6-core Intel Core i5 and 72 GB of RAM. It's a fantastic machine. It works perfectly, handles my development projects without any problems, and could easily serve me for several more years. I've been developing software for over 20 years, and I understand that technology moves forward. I have nothing against Apple Silicon. But forcing developers to replace perfectly functional and expensive computers just to continue publishing apps on the App Store is extremely disappointing. With the new SDK requirements coming in April 2027, many independent developers will be affected by this decision. Apple regularly talks about sustainability, environmental responsibility and reducing electronic waste. Yet here we are, being pushed towards replacing computers that are still more than capable of doing their jobs. I think Apple should hear from more of us. If you're in a similar situation, please consider sending feedback directly to Apple. You can use the message below. Feel free to copy it, personalise it, and submit it through Apple's Feedback Assistant: https://feedbackassistant.apple.com/ Subject: Please reconsider dropping Intel Mac support in Xcode 27 ================ Dear Apple Team, I would like to express my disappointment with the decision to discontinue Intel Mac support in Xcode 27. Many of us still use powerful, fully functional Intel Macs for professional software development. These computers are perfectly capable of handling our daily work and could remain useful for years to come. We understand and support technological progress, including the transition to Apple Silicon. However, we believe developers should not be forced to replace otherwise capable hardware simply to meet new App Store submission requirements. This decision particularly affects independent developers and small businesses, for whom replacing expensive equipment represents a significant and unnecessary cost. We also believe that extending the useful life of existing computers would better reflect Apple's commitment to sustainability and reducing electronic waste. We are not asking Apple to support Intel Macs forever. We are asking for a more reasonable transition period or an official solution that would allow developers to continue building and submitting apps using their existing hardware. Please reconsider this decision and listen to the developers who have supported Apple's ecosystem for many years. Thank you. ================ If you agree, please share your experience and send your own feedback to Apple. One message might not change anything, but if enough developers express their concerns, perhaps Apple will at least reconsider its approach. We have invested in Apple's ecosystem for years. I believe it's reasonable to expect Apple to respect that investment. Our computers haven't suddenly become useless. We should be able to keep using them while they're still capable of doing the job.
0
0
152
2d
Xcode Needs an Integrated Terminal
Hello Apple Developer Team! I'd like to suggest adding a native integrated terminal to Xcode. Xcode is a great development environment, but the lack of a built-in terminal creates unnecessary context switching between the IDE and Terminal or iTerm2. This is more than just a minor inconvenience. At my workplace, several developers prefer alternative editors for iOS development simply because they provide an integrated command line. A native terminal panel in Xcode, similar to those available in other modern IDEs, would make everyday development much more convenient. Ideally, it would support interactive shells (Zsh or Bash), persistent sessions, multiple tabs, and easy access through a keyboard shortcut. I recently experimented with creating an improvised terminal in Xcode using Bash and Custom Behaviors. It works for simple commands, but obviously cannot replace a proper integrated terminal. I believe this would be a valuable addition to Xcode and would help keep developers within Apple's own development environment. Please consider adding this feature. We'd really appreciate it! Final thoughts I believe an integrated terminal would be a valuable addition to Xcode and would help developers avoid unnecessary context switching. Other development environments have demonstrated how convenient this functionality can be. What do you think? Would you like to see a native terminal in Xcode as well? I'd be interested to hear the community's thoughts and whether this feature is already being considered. Thank you!
1
0
81
2d
Simulator and Canvas 27.3 "identityservicesd quit unexpectedly"
Anyone working with the 27.3 devices beta in Xcode 27.3 on macOS 27.3? Canvas and device hub/simulator are throwing this error while open, several on first load, then periodically (not sure of the periodicity). Any help is appreciated. Not sure if it's impacting at the code or app, but it is interfering with active work (it assumes modal position while working). Can reproduce from Device Hub only (all other apps, including XCode closed), screencast here - demos 27.2 for the time it is started no errors, 27.3 as soon as it is started "identityservicesd quit unexpectedly" errors. Looks like stages in the rendering also - noticed dock not displayed, error, then dock displayed, next - home icons not displayed, error, then home icons displayed, etc. https://app.screencast.com/iK0BaVIVpjt0O
6
4
507
2d
UIDesignRequiresCompatibility = YES causes a crash on iOS 26 when built with Xcode 27. The key seems to follow the runtime OS, not the build SDK
Hi, I ran into a behavior of UIDesignRequiresCompatibility that doesn't match how I (and probably others) read the documentation. Environment Xcode: 27.2 Base SDK: iOS 27.2 Deployment target: iOS 18 Run destination: iOS 26.6 (physical device) Documentation The documentation states: "The system ignores this key when you build for iOS 27 or later, iPadOS 27 or later, Mac Catalyst 27 or later, macOS 27 or later, or tvOS 27 or later." I read "build for iOS 27" as a build-time condition: once the app is built with the iOS 27 SDK, the key no longer has any effect, whatever OS the app runs on. What I observed With UIDesignRequiresCompatibility = YES in Info.plist, I built the app against the iOS 27 SDK and ran it on iOS 26.6. The app crashes at launch. I removed only that key, did a clean build with the same configuration, and ran on the same iOS 26.6 device. The app runs normally. So in practice the key is not ignored for an app built for iOS 27. It looks like the decision is made by the OS the app runs on: iOS 27+ ignores the key, but iOS 26 still reads and applies it to a binary linked against the iOS 27 SDK, and that combination crashes. Questions What does "build for iOS 27 or later" refer to: the SDK the app is built with, the deployment target, or the OS the app runs on? My deployment target is iOS 18, so the app still runs on iOS 26. If the key is still honored there even when the app is built with the iOS 27 SDK, could the documentation say so explicitly? Is compatibility mode on iOS 26 for an app linked against the iOS 27 SDK an unsupported combination, and is the crash expected? Should developers simply remove the key when they adopt the iOS 27 SDK and still support iOS 26? Thanks!
Topic: UI Frameworks SubTopic: General Tags:
0
0
98
2d
Apple Watch won’t show PIN when pairing in Device Hub (Solved)
Xcode 27 Beta 3 / watchOS 27 Beta 3 - Apple Watch won’t show PIN when pairing in Device Hub (Solved) I ran into an issue where my Apple Watch could no longer pair with Xcode after I manually removed it from Device Hub. Environment Xcode 27 Beta 3 macOS Tahoe Beta iOS 27 Beta 3 watchOS 27 Beta 3 Symptoms iPhone appears in Device Hub and is Connected. Apple Watch does not appear in Device Hub. On Apple Watch: Settings → Privacy & Security → Developer Mode → Devices My Mac appears in the list. Tapping the Mac: Enter watch passcode. Tap Pair. Expected: Xcode should display a 6-digit PIN. Actual: Xcode remains on “Waiting to Pair” forever. No PIN is shown. Additional observations Running: xcrun devicectl list devices Only shows the iPhone. The Apple Watch never appears. Also, while reproducing the issue, coredeviced receives no pairing request at all. So it doesn’t look like the pairing challenge is failing—the pairing request never reaches the Mac. Things I tried (none worked) Restarted Mac, iPhone and Apple Watch. Removed pairing from Device Hub. Removed the Mac from Apple Watch Developer Mode → Devices. Turned Developer Mode off/on. Erased and re-paired the Apple Watch with the iPhone. Re-enabled wireless development. None of these solved the issue. Solution What finally worked was surprisingly simple: Completely power off the iPhone. Keep the Apple Watch and Mac powered on. Pair the Apple Watch from Device Hub again. Immediately after the iPhone was powered off, Xcode displayed the pairing PIN and the pairing completed successfully. After the watch was paired, I powered the iPhone back on and everything continued to work normally. My guess It seems the iPhone (the companion device) may be holding a stale developer pairing state after the watch is manually unpaired from Device Hub. With the iPhone powered off, the watch appears to communicate directly with the Mac, allowing the pairing challenge to be created successfully. Hopefully this helps anyone else who gets stuck at “Waiting to Pair” with no PIN appearing.
1
4
882
3d
SKTestSession.setSimulatedError does not work - Products load successfully despite error configuration
Description I'm attempting to test error handling in my StoreKit implementation using SKTestSession.setSimulatedError(), but it doesn't trigger any errors. All StoreKit APIs (.loadProducts, .purchase, .appTransaction) succeed despite error simulation being configured before API calls. According to Apple's documentation, setSimulatedError(_:forAPI:) should cause the specified API to throw an error, but this doesn't happen in my testing environment. Background / Known issue I found a previous forum discussion: "SKTestSession.setSimulatedError() not working for .loadProducts API in iOS 26.2" which mentioned this was a bug in iOS 26.2 and was supposedly fixed in iOS 26.3. However, I'm experiencing the same issue in my current environment (Xcode 26.6 / iOS 26.5), which suggests either: The bug has regressed, or There's a different underlying issue, or I'm missing something in my implementation I wanted to report this to confirm whether this is still a known issue or if additional steps are needed. Environment Xcode: 26.6 Test Environment: iOS Simulator - iPhone 17 Pro(26.5) Testing Framework: XCTest StoreKitTest Framework: Included in Xcode Code Unit test code import XCTest import StoreKit import StoreKitTest final class StoreKitErrorTests: XCTestCase { func test_LoadProducts_SetSimulatedError() async throws { // Arrange let session = try SKTestSession(configurationFileNamed: "storekit") session.clearTransactions() session.disableDialogs = true // Set simulated error for loadProducts API try await session.setSimulatedError( .generic(.unknown), forAPI: .loadProducts ) // Act - Attempt to load products do { let products = try await Product.products(for: ["com.example.app.testproduct"]) // This line executes - products were loaded successfully print("[TEST] FAIL: Loaded \(products.count) products") XCTFail("setSimulatedError did not work - products loaded successfully") } catch { // This should execute, but it doesn't print("[TEST] PASS: Error was thrown") } } }.storekit file Note: Showing only the product definition. File also contains settings and version info. { "products" : [ { "displayPrice" : "1.23", "familyShareable" : false, "internalID" : "5AE6F98A", "localizations" : [ { "description" : "Test app", "displayName" : "LsStorekit", "locale" : "en_US" } ], "productID" : "com.example.app.testproduct", "referenceName" : "LsStorekit", "type" : "NonConsumable" } ] }Expected Behavior The Product.products(for:) call should throw an error because setSimulatedError(.generic(.unknown), forAPI: .loadProducts) was called before the API invocation. The test should: Configure the simulated error Attempt to load products Catch an error in the catch block Test passes with: "[TEST] PASS: Error was thrown" Actual Behavior Products are loaded successfully despite the error simulation: • The do block completes without throwing • 1 product is returned from Product.products(for:) • XCTFail() is called, indicating the error simulation didn't work • Test fails with: "[TEST] FAIL: Loaded 1 products" Console Output [TEST] FAIL: Loaded 1 products Additional Testing I've tested setSimulatedError with multiple APIs, and all show the same behavior: APIError configurationResult.loadProducts.generic(.unknown)No error thrown.purchase.generic(.unknown)No error thrown.appTransaction.generic(.unknown)No error thrown.appStoreSync.generic(.unknown)No error thrownWhat I've Already Tried • Calling setSimulatedError before app launch (in UI tests) • Calling setSimulatedError after app launch but before API calls • Using different error types (.generic(.unknown), .generic(.networkError(...))) • Testing in both Unit Tests and UI Tests • Using different APIs (.loadProducts, .purchase, .appTransaction) • Clearing transactions and resetting session state • Verifying the .storekit file is correctly loaded (products load successfully) • Running the app first (⌘R) to ensure StoreKit configuration is registered with the StoreKit daemon - This was necessary to fix an initial issue where products weren't loading at all Questions Is this a known limitation of SKTestSession.setSimulatedError()? Are there additional steps required to make error simulation work? Is there an alternative approach to test StoreKit error handling? Does this work in specific Xcode/iOS SDK versions only? Any guidance would be greatly appreciated. I need to test error handling in my StoreKit implementation, but cannot find a way to simulate errors reliably.
0
0
33
3d
Xcode shows my role as "Admin" on a new team and blocks creating a Developer ID Application certificate
Hi everyone, I enrolled in the Apple Developer Program a few days ago and received the enrollment-complete email. I enrolled myself, I am the only member, and I should be the Account Holder. What I see Xcode > Settings > Accounts shows one Apple ID with one team. The Role is "Admin", not Account Holder or Agent. The team page in Xcode shows a green check for Certificates, Identifiers & Profiles. However, on developer.apple.com, I can open Certificates, Identifiers & Profiles, and the site lists me as both Account Holder and Admin. In Xcode, Manage Certificates > + > Developer ID Application fails. The message says only the Account Holder can create it. What I already tried Signed out of my Apple ID in Xcode, quit Xcode, and signed back in. Confirmed that I have only one Apple ID and only one team. Environment Xcode: 27.2 macOS: 27.2.1 Golden Gate Questions Is "Admin" simply how Xcode labels the Account Holder on a single-member team, or does it mean my role is really Admin? What does Xcode check before it allows a Developer ID Application certificate? Could it be missing cloud-managed Developer ID certificate access on a new team? Is there anything I can fix myself, or does Apple need to change something on the account? Note: I don't want to do any manual steps after spending a good amount of money for enrollment. I have also opened a Developer Support request. Screenshots are attached. Thank you!
5
0
223
3d
Error 90068: iOS 11 build accepted in early September, now MinimumOSVersion 11.0 is rejected
Hello, I’m looking for clarification and guidance regarding a recent App Store Connect upload validation change that is preventing us from delivering an important bug-fix update to existing users on legacy iOS versions. Our production iOS app has historically supported iOS 11 and later. On August 28, 2026, we successfully uploaded a build with: MinimumOSVersion = 11.0 The upload completed successfully, with warnings only. One of the warnings stated: “MinimumOSVersion too low. This app has a MinimumOSVersion of 11.0. Starting later this year, all iOS apps must have a MinimumOSVersion of 13.0 or later in order to be uploaded to App Store Connect or submitted for distribution.” No specific enforcement date was provided. The same upload also displayed another warning stating: “Starting in Spring 2027, all iOS apps must have a MinimumOSVersion of 15.0 or later…” We subsequently uploaded another build targeting iOS 11 around September 8, and that version was successfully released on the App Store on September 10, 2026. I no longer have a screenshot of the warning from that particular upload, but the build itself was accepted and the corresponding version was released successfully. However, on September 17, 2026, when attempting to upload our next bug-fix build with the same MinimumOSVersion of 11.0, Apple’s server-side validation rejected the build with: Error 90068 “This bundle is invalid. The value provided for the key MinimumOSVersion '11.0' is not acceptable.” This means that the server-side enforcement appears to have changed sometime after our successful upload around September 8 and before September 17. What is especially confusing is that: the previous warning only said that iOS 13 would become mandatory “later this year”, without providing a specific enforcement date; iOS 11 builds were still being accepted in early September, including the build that was released on September 10; the same validation dialog stated that iOS 15 would become mandatory only in Spring 2027; the upload now fails completely before the build reaches App Store Connect or TestFlight. Because validation fails during upload, we cannot submit this build to App Review or request an expedited review. We have already completed a final bug-fix release for our existing legacy iOS users. Our intention is not to continue supporting iOS 11 indefinitely. We plan to increase the minimum supported iOS version after this release. We are only trying to deliver one final bug-fix update to users who already have the application installed on legacy iOS versions. The fix is ready, but affected production users currently have no way to receive it. I opened Apple Developer Support Case ID 102966589079 on September 17, 2026 and sent a follow-up on September 21. So far I have only received automated acknowledgements. The Developer Support case history also shows: “Email with Apple Developer Support — September 19, 2026” but I did not receive any email from Apple on that date. I checked Inbox, Spam/Junk, and Trash. Phone support for this case currently shows: “Phone support is currently unavailable due to high call volumes.” I have attached screenshots showing: the successful August 28 upload with the iOS 13 / iOS 15 warnings; the current Error 90068 rejection; the support case history. Could Apple please clarify: On what exact date did the MinimumOSVersion 13 requirement begin being enforced? Was this enforcement date announced anywhere before it became a hard upload requirement? Is there any supported way to upload one final bug-fix build for existing legacy iOS users? Could Case ID 102966589079 please be routed to the appropriate App Store Connect / Distribution team? Thank you.
5
0
1.1k
4d
Every Xcode Cloud build cancelled within seconds since 21 Oct 2026, no reason given, App Store Connect Xcode Cloud page blank (whole team)
Hello, Since 21 October 2026 at about 16:07 UTC, every Xcode Cloud build for our team is cancelled 5–6 seconds after it starts. This happens across two products, two GitHub repositories and every workflow. Before that date Xcode Cloud worked normally, and we have used roughly 11 of our compute hours. What happens • A build is created, then marked COMPLETE / CANCELED about 6 seconds later. • startedDate is null, cancelReason is null, and there are no actions, no logs and no builds. • It happens whether the build starts from a push, from the App Store Connect website or from the App Store Connect API. • It happens with the simplest possible workflow: one Archive action on "Latest Release" (Xcode 27.2, 27B52, and macOS Golden Gate 27.2, 26B123). Specific Xcode versions (27.1, 27A9275) fail the same way. • Product 1: runs #99–#105 were all cancelled. The latest are #104 and #105 on 15 Nov 2026. • Product 2: runs #136–#140 were all cancelled, across several days from 23 Oct 2026.Other symptoms • appstoreconnect.apple.com/xcode-cloud shows a blank white page, in normal and private windows, in more than one browser. The app pages in App Store Connect show no Xcode Cloud tab. • In Xcode on my Mac, the Xcode Cloud screens say "Unauthenticated", even though I'm signed in to my developer account in Xcode. The Mac is a MacBook Pro (15-inch, 2017), macOS Ventura 13.7.8 (22H730), Xcode 15.2 (15C500b). We don't build on this Mac; it only manages Xcode Cloud. • scmRepositories.lastAccessedDate stopped updating at 21 Oct 2026, 15:57 UTC for one repository, minutes before the cancellations began, and now returns null for both repositories.What we've already tried 1. Reinstalling GitHub access: uninstalled and reinstalled the Xcode Cloud GitHub app with access to all repositories, and re-granted access. No change. 2. Confirming Apple can see the code: the App Store Connect API still lists our branches and commits, and Xcode Cloud shows the right commit message on each cancelled build. 3. Removing extra workflows: removed every workflow except one plain Archive workflow. Still cancelled. 4. Checking the account: the developer membership is active, and all agreements in App Store Connect are accepted. 5. Checking uploads elsewhere: builds made on another CI system (GitHub Actions, Xcode 26.6) upload to TestFlight and pass App Review submission normally on the same account. Only Xcode Cloud is affected. 6. Checking Apple's System Status: shows no Xcode Cloud problems. 7. Contacting Developer Support: case 103005804006. Support pointed us to the forums.One possible trigger: on 21 Oct 2026, between 15:52 and 16:53 UTC, we created three new test workflows through the App Store Connect API. Their test destinations included an iOS 17.5 simulator alongside Xcode 27 and a newer-device simulator on iOS 27.1. The cancellations began minutes later. We have since deleted those workflows, and builds are still cancelled. Our question: it looks as if our team's Xcode Cloud setup on Apple's side is stuck or broken, which would explain both the blank page and the instant cancellations. Could someone on the Xcode Cloud team check our account and reset it? I'm happy to share the team ID and build run IDs privately. Thank you.
0
0
60
5d
Build behaving differently in testflight compared to simulator
Hi all I have an app I’m pretty much done with, and on the Xcode simulator it works perfectly and the IAP shows us when the purchase buttons are clicked but for some reason when it goes to testflight none of the buttons respond, is there any reason that would cause it to behave differently in testflight when its coded correctly and works in the simulator. thanks
1
0
608
1w
Bundle identifier after moving from a Personal Team to a paid Apple Developer Program enrollment
Application Group identifier unavailable after moving from a Personal Team to a paid Apple Developer Program enrollment Hi everyone, I built an app in Xcode using a Personal Team (free, signed in with my Apple ID) with the bundle identifier com.jcsnp.Minutely. My paid Apple Developer Program enrollment has been active since 5 Nov 2026, and I'm now trying to build and run the app under the new team. Xcode is blocking me on the App Group and the provisioning profile. Environment macOS 27, Xcode 27.2, iOS target 26.6 Paid enrollment: individual account, active since 5 Nov 2026 Errors Communication with Apple failed. An Application Group with Identifier 'group.com.jcsnp.Minutely' is not available. Please enter a different string. No profiles for 'com.jcsnp.Minutely' were found Xcode couldn't find any iOS App Development provisioning profiles matching 'com.jcsnp.Minutely'. What I've tried Cleaning the build folder. The errors remain. Questions The App Group group.com.jcsnp.Minutely is reported as unavailable. Is it still registered to my old Personal Team, or to another account? If so, how do I release it or move it to the new team? Does the Personal Team's registration of the bundle ID need to be removed before com.jcsnp.Minutely can be registered under the paid team? Is there a recommended order for setting this up: registering the App ID and App Group in the developer portal first, then letting Xcode generate the profile? Thanks in advance for any guidance.
5
0
356
1w
Unable to install iOS 18 simulator using xcodebuild 27
We are planning to upgrade our CI setup to run on Xcode 27, but we want to run tests on several older iOS simulator runtimes: 26, 18, 17… With Xcode 26.6, we had no trouble installing the needed runtimes by running: $ xcodebuild -downloadPlatform iOS -buildVersion 18.6 $ xcodebuild -downloadPlatform iOS -buildVersion 17.5 $ xcodebuild -downloadPlatform iOS -buildVersion 16.4 When using Xcode 27.0 (27A266a), however, the command fails to work for any runtime older than iOS 26.0: $ xcodebuild -downloadPlatform iOS -buildVersion 18.6 Finding content... iOS 18.6 is not available for download. At the same time, the runtimes can be installed just fine by using the "Add Platforms…" dialog from the Components pane in Xcode settings. Unfortunately, that's not an option in a headless CI machine. The same issue also reproduces in the beta versions 27.1 (27A9269) and 27.2 (27B5019j), and regardless of macOS version (26.7 or 27.0). Any idea how to work around the issue? I wonder if's a broken backend configuration or a regression in Xcode 27? Posted as FB24836279.
1
3
707
1w
ITMS-90383: Upload limit reached
Apple has blocked uploads from my account for at least two days with ITMS-90383: "The upload limit for your account has been reached. Please wait 1 day and try again." The block is on the account, not on any one app. They have all been refused. I read the emails in full, and Apple's own headers give their sent times as 9 Nov 21:10:48 GMT and 10 Nov 00:31:29 GMT. The last uploads that went through finished at about 21:04 GMT on 9 Nov. Failing runs began at about 20:56–21:10 GMT. So the block started at about 1 pm Pacific on 9 Nov. The app records the email as received at 19:55:55 GMT on 10 Nov, but Apple sent it at 21:10:48 GMT on 9 Nov. That is about 22 hours and 45 minutes later. So the first warning reached my inbox about a day after Apple sent it, and more pushes went out in that gap. Why was the delivery so late? Questions: The exact limit. Apple doesn't publish it. Forum posters report being blocked at about 19–20 uploads a day. Whether rejected retries extend the block. The cause of each individual failed run. Some failed for other reasons. For example, Tech build 3 failed on the macOS archive. Nothing I've found points to the app code. This is Apple's cap. From App Store Connect <no_reply@email.apple.com> Action needed: The uploaded build for ... has one or more issues. App Store Connect Hello, We noticed one or more issues with a recent delivery for the following app: App Apple ID Version 1.0 Build 5 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90383: Upload limit reached - The upload limit for your account has been reached. Please wait 1 day and try again. Apple Developer Relations
1
0
95
1w
Resolving a "Simulator runtime is not available" error
Some Macs recently received a macOS system update which disabled the simulator runtimes used by Xcode 15, including the simulators for iOS, tvOS, watchOS, and visionOS. If your Mac received this update, you will receive the following error message and will be unable to use the simulator: The com.apple.CoreSimulator.SimRuntime.iOS-17-2 simulator runtime is not available. Domain: com.apple.CoreSimulator.SimError Code: 401 Failure Reason: runtime profile not found using "System" match policy Recovery Suggestion: Download the com.apple.CoreSimulator.SimRuntime.iOS-17-2 simulator runtime from the Xcode To resume using the simulator, please reboot your Mac. After rebooting, check Xcode Preferences → Platforms to ensure that the simulator runtime you would like to use is still installed. If it is missing, use the Get button to download it again. The Xcode 15.3 Release Notes are also updated with this information.
Replies
0
Boosts
0
Views
11k
Activity
May ’24
Questions about swift student challenge 27
I'm excited to see the announcement of Swift Student Challenge 27, but I have a couple of questions: The rules mention that Xcode Apps are allowed. Does this mean we can create and submit a folder containing an .xcodeproj file instead of a .swiftpm Swift Playgrounds package? While it's great to see support across all Apple platforms this year, I'm a bit concerned about whether the judges will test submissions on physical devices or in the simulator. I had a similar concern last year (https://developer.apple.com/forums/thread/812429). Thanks!
Replies
2
Boosts
0
Views
177
Activity
4h
Supported way to supervise an iOS Simulator XCTest host before application code executes?
We are investigating a supported architecture for running existing app-hosted XCTest unit and integration tests in iOS Simulator under external process supervision. Our environment is Xcode 27.2, targeting ARM64 iOS Simulator. The tests use SwiftData, CoreData and SQLite with synthetic, test-owned databases. We need to run selected tests serially in isolated processes, monitor their resource usage, and verify that all test-related processes have terminated before cleaning up test databases. Our primary question: Is there a documented, supported way to establish external process supervision before the actual iOS Simulator XCTest host executes any application or test-bundle code? In particular, we are looking for guidance on the following: Pre-execution control: Can the actual XCTest host be launched suspended and released only after an external supervisor has established monitoring? We need coverage of application and test-bundle initialization, not merely a callback before the first test method. Process identity: Is there a supported mechanism to identify and monitor the actual host process using an OS-verifiable identity that remains reliable despite PID reuse? Process termination: Is there a supported way to identify and terminate only the processes belonging to a specific test run, including detached or reparented children, without affecting unrelated Simulator processes? XCTest integration: Can this be achieved while preserving normal XCTest discovery, setup/teardown, asynchronous tests and genuine .xcresult reporting? We have investigated public XCTest APIs, standard xcodebuild workflows and macOS process-control mechanisms. We also successfully compiled and linked a separate ARM64 Simulator executable against our unchanged application debug dylib and XCTest dependencies. However, this was strictly a compile/link experiment: the executable was never launched, and we have not established that a custom XCTest host is supported. We are not seeking private APIs or undocumented CoreSimulator behavior. If this level of supervision is not supported, what is Apple’s recommended documented alternative? In particular, does the standard Xcode-managed XCTest workflow provide any documented guarantees regarding host process identity, lifecycle containment and complete termination of test-related processes? References to official documentation or supported examples would be greatly appreciated.
Replies
0
Boosts
0
Views
26
Activity
1d
Apple Watch SE 3 fails to pair with Xcode Device Hub: protocol_shoes does not support endpoint type 3
Hi all, I cannot pair a physical Apple Watch SE 3 with Xcode, and I would like to know if anyone else sees this or has found a workaround. Environment Apple Watch SE 3 (GPS, Watch7,13), watchOS 27.2.1 (24S132) Companion iPhone 15 Plus, iOS 27.2 (24B119) Tested on two different Macs: a MacBook Air (macOS 27.2.1, Xcode 27.2) and an iMac Developer Mode is enabled on both the iPhone and the Watch The iPhone is trusted, connects to the Mac, and appears in Device Hub Problem The Watch shows “Pair with <Mac name>” in its Developer Mode settings. When I tap it, pairing does not complete and the Watch does not appear in Device Hub. Watch log (remotepairingdeviced). The sysdiagnose shows the pairing request failing within about 20 ms. Log prefixes and the endpoint address are omitted: Received request to wirelessly pair from peer Path is satisfied; interface: ipsec2; uses wifi, proxy Endpoint type is not an address or host, cannot synthesize URL protocol_shoes does not support endpoint type 3 Failed to attach application protocol shoes Received pairing outcome failure (errorCode: -1, "An unknown error occurred.")What I tried Restarted the Watch, iPhone and Mac Tested on two Macs and on different Wi-Fi networks Turning Bluetooth off on the iPhone: the Watch then no longer discovers the Mac at all The same failure appears in the Watch sysdiagnoses for all attempts. I filed a report in Feedback Assistant: FB25623613 Has anyone seen this error or found a workaround? Thanks
Replies
0
Boosts
0
Views
48
Activity
1d
Accessibility Inspector Element Detection and contrast failures with SwiftUI sheets
I am investigating Accessibility Inspector/XCTest audit results in a SwiftUI app (Target Keeper), without suppressing warnings. Environment: Xcode 27.1 (27A9275), iPadOS 27.0 Simulator, macOS 27.0.1. Debug and Release builds pass. The app uses scalable text and labeled controls. Element Detection / native sheet Main-screen Element Detection passes when the sheet is closed. With a SwiftUI .sheet presented, the iPad audit reports “Potentially inaccessible text”; XCUIAccessibilityAuditIssue.element is nil. Exported Inspector HTML highlights background labels behind/outside the sheet, rather than a foreground control. The separate, data-free SwiftUI application below reproduces the modal-only warning; it links no application modules or persistence. Actual iPad Simulator VoiceOver testing using XCUIDevice.shared.voiceOverService passes forward/backward traversal of the real application's modal controls, without reaching the background labels. This is simulator evidence, not physical-device acceptance. A trial explicit modal container/.isModal trait did not clear the audit and was reverted; no warnings are filtered. Minimal independent app: import SwiftUI @main struct ModalRepro: App { @State private var showing=false private let names=["Vegetables","Protein","Fruit","Dairy","Grains","Healthy Fats"] var body:some Scene {WindowGroup { NavigationStack { VStack(spacing:24) { Button("Nutrition") {}.accessibilityLabel("Choose Page").accessibilityValue("Nutrition") LazyVGrid(columns:[GridItem(.flexible()),GridItem(.flexible()),GridItem(.flexible())],spacing:40) { ForEach(names,id:\.self) { name in Button {} label: { VStack(spacing:10) { Circle().fill(.blue.opacity(0.3)).frame(width:250,height:250) Text(name).font(.system(size:17)).accessibilityHidden(true) } }.buttonStyle(.plain).accessibilityLabel(name) } } Button("Show modal") {showing=true} }.padding(24).frame(maxWidth:.infinity,maxHeight:.infinity).background(Color.black) }.preferredColorScheme(.dark) .sheet(isPresented:$showing) { NavigationStack { VStack {Text("Foreground content");Button("Close") {showing=false}} .frame(maxWidth:.infinity,maxHeight:.infinity).background(Color.black) .navigationTitle("Modal flow") }.preferredColorScheme(.dark) } }} }In an Xcode UI-test target, launch this app, run try app.performAccessibilityAudit(for: [.elementDetection]), tap “Show modal”, then run the same audit again. The first passes and the second fails. No issue handler ignores failures. Contrast / scrolling — separate unresolved finding All four iPhone combined-audit configurations (portrait/landscape, normal/maximum Dynamic Type) pass in the tested picker state. However, iPad maximum-text combined audits and a separate scrolled iPhone maximum-text landscape contrast audit still fail; we are not calling these resolved. In the scrolled iPhone case, XCTest identifies a count label whose frame is entirely above the visible results viewport. Inspector's exported HTML reports 1.37:1 using #252526 versus #000000; its marked screenshot rectangle overlaps the dark search/header area, not visible count text. Visible sampled labels instead have white or light foregrounds on opaque dark fills (e.g. #FFFFFF/#1C1C1E = 17.01:1; #98989F/#1C1C1E = 5.94:1). These are screenshot core-pixel measurements, not proof every warning is false. We compare ordinary text against 4.5:1 and interactive non-text against 3:1. iPad maximum-text warnings have not yet been matched to an exact visible color pair. Original failures and HTML exports are preserved privately. Questions Is Element Detection expected to inspect background elements behind a presented native SwiftUI sheet? Is this a known tool limitation/framework issue, or does the sample need different semantics? What is the supported way to establish modal accessibility boundaries with SwiftUI sheets, and when should .isModal be added explicitly? How should we distinguish a real contrast defect from clipping, occlusion, translucency, or sampling of an offscreen element? Which Inspector export fields/diagnostics should establish the actual sampled text/background pair? What additional evidence/manual and physical-device tests does Apple recommend before qualifying accessibility when the minimal audit reproduction fails but actual VoiceOver modal focus behaves correctly? We are not asking to waive audits or declare full accessibility from a VoiceOver pass alone. I read Apple's audit guidance and modal trait documentation: https://developer.apple.com/documentation/accessibility/performing-accessibility-audits-for-your-app https://developer.apple.com/documentation/swiftui/accessibilitytraits/ismodal https://developer.apple.com/help/app-store-connect/manage-app-accessibility/sufficient-contrast-evaluation-criteria/ Related discussion https://developer.apple.com/forums/thread/823968 recommends Feedback for a different apparent Dynamic Type false positive; it does not answer these modal/contrast questions. A Feedback draft is prepared but not submitted, so I have no Feedback ID yet. No private data, identifiers, credentials, app containers or confidential application source are included.
Replies
2
Boosts
0
Views
1.2k
Activity
1d
Documentation in Xcode not downloading
Switched to Xcode 27.2 and it started downloading documentation. After download is finished documentation window is empty, prompting to look up documenation online or download it. Triggering any download does not help – no documentation is available. (Sidenote: Reinstalled Xcode 27.2 and documentation was there. But Xcode started a download automatically and without confirmation and afterwards it is gone)
Replies
2
Boosts
2
Views
94
Activity
1d
Xcode 27 and Intel Macs: Let's Make Our Voices Heard
I would like to express my disappointment with Apple's decision to drop Intel Mac support in Xcode 27, and I believe we should speak up about it. I'm still using my 27-inch Retina 5K iMac from 2020, with a 3.3 GHz 6-core Intel Core i5 and 72 GB of RAM. It's a fantastic machine. It works perfectly, handles my development projects without any problems, and could easily serve me for several more years. I've been developing software for over 20 years, and I understand that technology moves forward. I have nothing against Apple Silicon. But forcing developers to replace perfectly functional and expensive computers just to continue publishing apps on the App Store is extremely disappointing. With the new SDK requirements coming in April 2027, many independent developers will be affected by this decision. Apple regularly talks about sustainability, environmental responsibility and reducing electronic waste. Yet here we are, being pushed towards replacing computers that are still more than capable of doing their jobs. I think Apple should hear from more of us. If you're in a similar situation, please consider sending feedback directly to Apple. You can use the message below. Feel free to copy it, personalise it, and submit it through Apple's Feedback Assistant: https://feedbackassistant.apple.com/ Subject: Please reconsider dropping Intel Mac support in Xcode 27 ================ Dear Apple Team, I would like to express my disappointment with the decision to discontinue Intel Mac support in Xcode 27. Many of us still use powerful, fully functional Intel Macs for professional software development. These computers are perfectly capable of handling our daily work and could remain useful for years to come. We understand and support technological progress, including the transition to Apple Silicon. However, we believe developers should not be forced to replace otherwise capable hardware simply to meet new App Store submission requirements. This decision particularly affects independent developers and small businesses, for whom replacing expensive equipment represents a significant and unnecessary cost. We also believe that extending the useful life of existing computers would better reflect Apple's commitment to sustainability and reducing electronic waste. We are not asking Apple to support Intel Macs forever. We are asking for a more reasonable transition period or an official solution that would allow developers to continue building and submitting apps using their existing hardware. Please reconsider this decision and listen to the developers who have supported Apple's ecosystem for many years. Thank you. ================ If you agree, please share your experience and send your own feedback to Apple. One message might not change anything, but if enough developers express their concerns, perhaps Apple will at least reconsider its approach. We have invested in Apple's ecosystem for years. I believe it's reasonable to expect Apple to respect that investment. Our computers haven't suddenly become useless. We should be able to keep using them while they're still capable of doing the job.
Replies
0
Boosts
0
Views
152
Activity
2d
Xcode Needs an Integrated Terminal
Hello Apple Developer Team! I'd like to suggest adding a native integrated terminal to Xcode. Xcode is a great development environment, but the lack of a built-in terminal creates unnecessary context switching between the IDE and Terminal or iTerm2. This is more than just a minor inconvenience. At my workplace, several developers prefer alternative editors for iOS development simply because they provide an integrated command line. A native terminal panel in Xcode, similar to those available in other modern IDEs, would make everyday development much more convenient. Ideally, it would support interactive shells (Zsh or Bash), persistent sessions, multiple tabs, and easy access through a keyboard shortcut. I recently experimented with creating an improvised terminal in Xcode using Bash and Custom Behaviors. It works for simple commands, but obviously cannot replace a proper integrated terminal. I believe this would be a valuable addition to Xcode and would help keep developers within Apple's own development environment. Please consider adding this feature. We'd really appreciate it! Final thoughts I believe an integrated terminal would be a valuable addition to Xcode and would help developers avoid unnecessary context switching. Other development environments have demonstrated how convenient this functionality can be. What do you think? Would you like to see a native terminal in Xcode as well? I'd be interested to hear the community's thoughts and whether this feature is already being considered. Thank you!
Replies
1
Boosts
0
Views
81
Activity
2d
Simulator and Canvas 27.3 "identityservicesd quit unexpectedly"
Anyone working with the 27.3 devices beta in Xcode 27.3 on macOS 27.3? Canvas and device hub/simulator are throwing this error while open, several on first load, then periodically (not sure of the periodicity). Any help is appreciated. Not sure if it's impacting at the code or app, but it is interfering with active work (it assumes modal position while working). Can reproduce from Device Hub only (all other apps, including XCode closed), screencast here - demos 27.2 for the time it is started no errors, 27.3 as soon as it is started "identityservicesd quit unexpectedly" errors. Looks like stages in the rendering also - noticed dock not displayed, error, then dock displayed, next - home icons not displayed, error, then home icons displayed, etc. https://app.screencast.com/iK0BaVIVpjt0O
Replies
6
Boosts
4
Views
507
Activity
2d
UIDesignRequiresCompatibility = YES causes a crash on iOS 26 when built with Xcode 27. The key seems to follow the runtime OS, not the build SDK
Hi, I ran into a behavior of UIDesignRequiresCompatibility that doesn't match how I (and probably others) read the documentation. Environment Xcode: 27.2 Base SDK: iOS 27.2 Deployment target: iOS 18 Run destination: iOS 26.6 (physical device) Documentation The documentation states: "The system ignores this key when you build for iOS 27 or later, iPadOS 27 or later, Mac Catalyst 27 or later, macOS 27 or later, or tvOS 27 or later." I read "build for iOS 27" as a build-time condition: once the app is built with the iOS 27 SDK, the key no longer has any effect, whatever OS the app runs on. What I observed With UIDesignRequiresCompatibility = YES in Info.plist, I built the app against the iOS 27 SDK and ran it on iOS 26.6. The app crashes at launch. I removed only that key, did a clean build with the same configuration, and ran on the same iOS 26.6 device. The app runs normally. So in practice the key is not ignored for an app built for iOS 27. It looks like the decision is made by the OS the app runs on: iOS 27+ ignores the key, but iOS 26 still reads and applies it to a binary linked against the iOS 27 SDK, and that combination crashes. Questions What does "build for iOS 27 or later" refer to: the SDK the app is built with, the deployment target, or the OS the app runs on? My deployment target is iOS 18, so the app still runs on iOS 26. If the key is still honored there even when the app is built with the iOS 27 SDK, could the documentation say so explicitly? Is compatibility mode on iOS 26 for an app linked against the iOS 27 SDK an unsupported combination, and is the crash expected? Should developers simply remove the key when they adopt the iOS 27 SDK and still support iOS 26? Thanks!
Topic: UI Frameworks SubTopic: General Tags:
Replies
0
Boosts
0
Views
98
Activity
2d
Apple Watch won’t show PIN when pairing in Device Hub (Solved)
Xcode 27 Beta 3 / watchOS 27 Beta 3 - Apple Watch won’t show PIN when pairing in Device Hub (Solved) I ran into an issue where my Apple Watch could no longer pair with Xcode after I manually removed it from Device Hub. Environment Xcode 27 Beta 3 macOS Tahoe Beta iOS 27 Beta 3 watchOS 27 Beta 3 Symptoms iPhone appears in Device Hub and is Connected. Apple Watch does not appear in Device Hub. On Apple Watch: Settings → Privacy & Security → Developer Mode → Devices My Mac appears in the list. Tapping the Mac: Enter watch passcode. Tap Pair. Expected: Xcode should display a 6-digit PIN. Actual: Xcode remains on “Waiting to Pair” forever. No PIN is shown. Additional observations Running: xcrun devicectl list devices Only shows the iPhone. The Apple Watch never appears. Also, while reproducing the issue, coredeviced receives no pairing request at all. So it doesn’t look like the pairing challenge is failing—the pairing request never reaches the Mac. Things I tried (none worked) Restarted Mac, iPhone and Apple Watch. Removed pairing from Device Hub. Removed the Mac from Apple Watch Developer Mode → Devices. Turned Developer Mode off/on. Erased and re-paired the Apple Watch with the iPhone. Re-enabled wireless development. None of these solved the issue. Solution What finally worked was surprisingly simple: Completely power off the iPhone. Keep the Apple Watch and Mac powered on. Pair the Apple Watch from Device Hub again. Immediately after the iPhone was powered off, Xcode displayed the pairing PIN and the pairing completed successfully. After the watch was paired, I powered the iPhone back on and everything continued to work normally. My guess It seems the iPhone (the companion device) may be holding a stale developer pairing state after the watch is manually unpaired from Device Hub. With the iPhone powered off, the watch appears to communicate directly with the Mac, allowing the pairing challenge to be created successfully. Hopefully this helps anyone else who gets stuck at “Waiting to Pair” with no PIN appearing.
Replies
1
Boosts
4
Views
882
Activity
3d
SKTestSession.setSimulatedError does not work - Products load successfully despite error configuration
Description I'm attempting to test error handling in my StoreKit implementation using SKTestSession.setSimulatedError(), but it doesn't trigger any errors. All StoreKit APIs (.loadProducts, .purchase, .appTransaction) succeed despite error simulation being configured before API calls. According to Apple's documentation, setSimulatedError(_:forAPI:) should cause the specified API to throw an error, but this doesn't happen in my testing environment. Background / Known issue I found a previous forum discussion: "SKTestSession.setSimulatedError() not working for .loadProducts API in iOS 26.2" which mentioned this was a bug in iOS 26.2 and was supposedly fixed in iOS 26.3. However, I'm experiencing the same issue in my current environment (Xcode 26.6 / iOS 26.5), which suggests either: The bug has regressed, or There's a different underlying issue, or I'm missing something in my implementation I wanted to report this to confirm whether this is still a known issue or if additional steps are needed. Environment Xcode: 26.6 Test Environment: iOS Simulator - iPhone 17 Pro(26.5) Testing Framework: XCTest StoreKitTest Framework: Included in Xcode Code Unit test code import XCTest import StoreKit import StoreKitTest final class StoreKitErrorTests: XCTestCase { func test_LoadProducts_SetSimulatedError() async throws { // Arrange let session = try SKTestSession(configurationFileNamed: "storekit") session.clearTransactions() session.disableDialogs = true // Set simulated error for loadProducts API try await session.setSimulatedError( .generic(.unknown), forAPI: .loadProducts ) // Act - Attempt to load products do { let products = try await Product.products(for: ["com.example.app.testproduct"]) // This line executes - products were loaded successfully print("[TEST] FAIL: Loaded \(products.count) products") XCTFail("setSimulatedError did not work - products loaded successfully") } catch { // This should execute, but it doesn't print("[TEST] PASS: Error was thrown") } } }.storekit file Note: Showing only the product definition. File also contains settings and version info. { "products" : [ { "displayPrice" : "1.23", "familyShareable" : false, "internalID" : "5AE6F98A", "localizations" : [ { "description" : "Test app", "displayName" : "LsStorekit", "locale" : "en_US" } ], "productID" : "com.example.app.testproduct", "referenceName" : "LsStorekit", "type" : "NonConsumable" } ] }Expected Behavior The Product.products(for:) call should throw an error because setSimulatedError(.generic(.unknown), forAPI: .loadProducts) was called before the API invocation. The test should: Configure the simulated error Attempt to load products Catch an error in the catch block Test passes with: "[TEST] PASS: Error was thrown" Actual Behavior Products are loaded successfully despite the error simulation: • The do block completes without throwing • 1 product is returned from Product.products(for:) • XCTFail() is called, indicating the error simulation didn't work • Test fails with: "[TEST] FAIL: Loaded 1 products" Console Output [TEST] FAIL: Loaded 1 products Additional Testing I've tested setSimulatedError with multiple APIs, and all show the same behavior: APIError configurationResult.loadProducts.generic(.unknown)No error thrown.purchase.generic(.unknown)No error thrown.appTransaction.generic(.unknown)No error thrown.appStoreSync.generic(.unknown)No error thrownWhat I've Already Tried • Calling setSimulatedError before app launch (in UI tests) • Calling setSimulatedError after app launch but before API calls • Using different error types (.generic(.unknown), .generic(.networkError(...))) • Testing in both Unit Tests and UI Tests • Using different APIs (.loadProducts, .purchase, .appTransaction) • Clearing transactions and resetting session state • Verifying the .storekit file is correctly loaded (products load successfully) • Running the app first (⌘R) to ensure StoreKit configuration is registered with the StoreKit daemon - This was necessary to fix an initial issue where products weren't loading at all Questions Is this a known limitation of SKTestSession.setSimulatedError()? Are there additional steps required to make error simulation work? Is there an alternative approach to test StoreKit error handling? Does this work in specific Xcode/iOS SDK versions only? Any guidance would be greatly appreciated. I need to test error handling in my StoreKit implementation, but cannot find a way to simulate errors reliably.
Replies
0
Boosts
0
Views
33
Activity
3d
Xcode shows my role as "Admin" on a new team and blocks creating a Developer ID Application certificate
Hi everyone, I enrolled in the Apple Developer Program a few days ago and received the enrollment-complete email. I enrolled myself, I am the only member, and I should be the Account Holder. What I see Xcode > Settings > Accounts shows one Apple ID with one team. The Role is "Admin", not Account Holder or Agent. The team page in Xcode shows a green check for Certificates, Identifiers & Profiles. However, on developer.apple.com, I can open Certificates, Identifiers & Profiles, and the site lists me as both Account Holder and Admin. In Xcode, Manage Certificates > + > Developer ID Application fails. The message says only the Account Holder can create it. What I already tried Signed out of my Apple ID in Xcode, quit Xcode, and signed back in. Confirmed that I have only one Apple ID and only one team. Environment Xcode: 27.2 macOS: 27.2.1 Golden Gate Questions Is "Admin" simply how Xcode labels the Account Holder on a single-member team, or does it mean my role is really Admin? What does Xcode check before it allows a Developer ID Application certificate? Could it be missing cloud-managed Developer ID certificate access on a new team? Is there anything I can fix myself, or does Apple need to change something on the account? Note: I don't want to do any manual steps after spending a good amount of money for enrollment. I have also opened a Developer Support request. Screenshots are attached. Thank you!
Replies
5
Boosts
0
Views
223
Activity
3d
Error 90068: iOS 11 build accepted in early September, now MinimumOSVersion 11.0 is rejected
Hello, I’m looking for clarification and guidance regarding a recent App Store Connect upload validation change that is preventing us from delivering an important bug-fix update to existing users on legacy iOS versions. Our production iOS app has historically supported iOS 11 and later. On August 28, 2026, we successfully uploaded a build with: MinimumOSVersion = 11.0 The upload completed successfully, with warnings only. One of the warnings stated: “MinimumOSVersion too low. This app has a MinimumOSVersion of 11.0. Starting later this year, all iOS apps must have a MinimumOSVersion of 13.0 or later in order to be uploaded to App Store Connect or submitted for distribution.” No specific enforcement date was provided. The same upload also displayed another warning stating: “Starting in Spring 2027, all iOS apps must have a MinimumOSVersion of 15.0 or later…” We subsequently uploaded another build targeting iOS 11 around September 8, and that version was successfully released on the App Store on September 10, 2026. I no longer have a screenshot of the warning from that particular upload, but the build itself was accepted and the corresponding version was released successfully. However, on September 17, 2026, when attempting to upload our next bug-fix build with the same MinimumOSVersion of 11.0, Apple’s server-side validation rejected the build with: Error 90068 “This bundle is invalid. The value provided for the key MinimumOSVersion '11.0' is not acceptable.” This means that the server-side enforcement appears to have changed sometime after our successful upload around September 8 and before September 17. What is especially confusing is that: the previous warning only said that iOS 13 would become mandatory “later this year”, without providing a specific enforcement date; iOS 11 builds were still being accepted in early September, including the build that was released on September 10; the same validation dialog stated that iOS 15 would become mandatory only in Spring 2027; the upload now fails completely before the build reaches App Store Connect or TestFlight. Because validation fails during upload, we cannot submit this build to App Review or request an expedited review. We have already completed a final bug-fix release for our existing legacy iOS users. Our intention is not to continue supporting iOS 11 indefinitely. We plan to increase the minimum supported iOS version after this release. We are only trying to deliver one final bug-fix update to users who already have the application installed on legacy iOS versions. The fix is ready, but affected production users currently have no way to receive it. I opened Apple Developer Support Case ID 102966589079 on September 17, 2026 and sent a follow-up on September 21. So far I have only received automated acknowledgements. The Developer Support case history also shows: “Email with Apple Developer Support — September 19, 2026” but I did not receive any email from Apple on that date. I checked Inbox, Spam/Junk, and Trash. Phone support for this case currently shows: “Phone support is currently unavailable due to high call volumes.” I have attached screenshots showing: the successful August 28 upload with the iOS 13 / iOS 15 warnings; the current Error 90068 rejection; the support case history. Could Apple please clarify: On what exact date did the MinimumOSVersion 13 requirement begin being enforced? Was this enforcement date announced anywhere before it became a hard upload requirement? Is there any supported way to upload one final bug-fix build for existing legacy iOS users? Could Case ID 102966589079 please be routed to the appropriate App Store Connect / Distribution team? Thank you.
Replies
5
Boosts
0
Views
1.1k
Activity
4d
Every Xcode Cloud build cancelled within seconds since 21 Oct 2026, no reason given, App Store Connect Xcode Cloud page blank (whole team)
Hello, Since 21 October 2026 at about 16:07 UTC, every Xcode Cloud build for our team is cancelled 5–6 seconds after it starts. This happens across two products, two GitHub repositories and every workflow. Before that date Xcode Cloud worked normally, and we have used roughly 11 of our compute hours. What happens • A build is created, then marked COMPLETE / CANCELED about 6 seconds later. • startedDate is null, cancelReason is null, and there are no actions, no logs and no builds. • It happens whether the build starts from a push, from the App Store Connect website or from the App Store Connect API. • It happens with the simplest possible workflow: one Archive action on "Latest Release" (Xcode 27.2, 27B52, and macOS Golden Gate 27.2, 26B123). Specific Xcode versions (27.1, 27A9275) fail the same way. • Product 1: runs #99–#105 were all cancelled. The latest are #104 and #105 on 15 Nov 2026. • Product 2: runs #136–#140 were all cancelled, across several days from 23 Oct 2026.Other symptoms • appstoreconnect.apple.com/xcode-cloud shows a blank white page, in normal and private windows, in more than one browser. The app pages in App Store Connect show no Xcode Cloud tab. • In Xcode on my Mac, the Xcode Cloud screens say "Unauthenticated", even though I'm signed in to my developer account in Xcode. The Mac is a MacBook Pro (15-inch, 2017), macOS Ventura 13.7.8 (22H730), Xcode 15.2 (15C500b). We don't build on this Mac; it only manages Xcode Cloud. • scmRepositories.lastAccessedDate stopped updating at 21 Oct 2026, 15:57 UTC for one repository, minutes before the cancellations began, and now returns null for both repositories.What we've already tried 1. Reinstalling GitHub access: uninstalled and reinstalled the Xcode Cloud GitHub app with access to all repositories, and re-granted access. No change. 2. Confirming Apple can see the code: the App Store Connect API still lists our branches and commits, and Xcode Cloud shows the right commit message on each cancelled build. 3. Removing extra workflows: removed every workflow except one plain Archive workflow. Still cancelled. 4. Checking the account: the developer membership is active, and all agreements in App Store Connect are accepted. 5. Checking uploads elsewhere: builds made on another CI system (GitHub Actions, Xcode 26.6) upload to TestFlight and pass App Review submission normally on the same account. Only Xcode Cloud is affected. 6. Checking Apple's System Status: shows no Xcode Cloud problems. 7. Contacting Developer Support: case 103005804006. Support pointed us to the forums.One possible trigger: on 21 Oct 2026, between 15:52 and 16:53 UTC, we created three new test workflows through the App Store Connect API. Their test destinations included an iOS 17.5 simulator alongside Xcode 27 and a newer-device simulator on iOS 27.1. The cancellations began minutes later. We have since deleted those workflows, and builds are still cancelled. Our question: it looks as if our team's Xcode Cloud setup on Apple's side is stuck or broken, which would explain both the blank page and the instant cancellations. Could someone on the Xcode Cloud team check our account and reset it? I'm happy to share the team ID and build run IDs privately. Thank you.
Replies
0
Boosts
0
Views
60
Activity
5d
Build behaving differently in testflight compared to simulator
Hi all I have an app I’m pretty much done with, and on the Xcode simulator it works perfectly and the IAP shows us when the purchase buttons are clicked but for some reason when it goes to testflight none of the buttons respond, is there any reason that would cause it to behave differently in testflight when its coded correctly and works in the simulator. thanks
Replies
1
Boosts
0
Views
608
Activity
1w
Bundle identifier after moving from a Personal Team to a paid Apple Developer Program enrollment
Application Group identifier unavailable after moving from a Personal Team to a paid Apple Developer Program enrollment Hi everyone, I built an app in Xcode using a Personal Team (free, signed in with my Apple ID) with the bundle identifier com.jcsnp.Minutely. My paid Apple Developer Program enrollment has been active since 5 Nov 2026, and I'm now trying to build and run the app under the new team. Xcode is blocking me on the App Group and the provisioning profile. Environment macOS 27, Xcode 27.2, iOS target 26.6 Paid enrollment: individual account, active since 5 Nov 2026 Errors Communication with Apple failed. An Application Group with Identifier 'group.com.jcsnp.Minutely' is not available. Please enter a different string. No profiles for 'com.jcsnp.Minutely' were found Xcode couldn't find any iOS App Development provisioning profiles matching 'com.jcsnp.Minutely'. What I've tried Cleaning the build folder. The errors remain. Questions The App Group group.com.jcsnp.Minutely is reported as unavailable. Is it still registered to my old Personal Team, or to another account? If so, how do I release it or move it to the new team? Does the Personal Team's registration of the bundle ID need to be removed before com.jcsnp.Minutely can be registered under the paid team? Is there a recommended order for setting this up: registering the App ID and App Group in the developer portal first, then letting Xcode generate the profile? Thanks in advance for any guidance.
Replies
5
Boosts
0
Views
356
Activity
1w
Unable to install iOS 18 simulator using xcodebuild 27
We are planning to upgrade our CI setup to run on Xcode 27, but we want to run tests on several older iOS simulator runtimes: 26, 18, 17… With Xcode 26.6, we had no trouble installing the needed runtimes by running: $ xcodebuild -downloadPlatform iOS -buildVersion 18.6 $ xcodebuild -downloadPlatform iOS -buildVersion 17.5 $ xcodebuild -downloadPlatform iOS -buildVersion 16.4 When using Xcode 27.0 (27A266a), however, the command fails to work for any runtime older than iOS 26.0: $ xcodebuild -downloadPlatform iOS -buildVersion 18.6 Finding content... iOS 18.6 is not available for download. At the same time, the runtimes can be installed just fine by using the "Add Platforms…" dialog from the Components pane in Xcode settings. Unfortunately, that's not an option in a headless CI machine. The same issue also reproduces in the beta versions 27.1 (27A9269) and 27.2 (27B5019j), and regardless of macOS version (26.7 or 27.0). Any idea how to work around the issue? I wonder if's a broken backend configuration or a regression in Xcode 27? Posted as FB24836279.
Replies
1
Boosts
3
Views
707
Activity
1w
ITMS-90383: Upload limit reached
Apple has blocked uploads from my account for at least two days with ITMS-90383: "The upload limit for your account has been reached. Please wait 1 day and try again." The block is on the account, not on any one app. They have all been refused. I read the emails in full, and Apple's own headers give their sent times as 9 Nov 21:10:48 GMT and 10 Nov 00:31:29 GMT. The last uploads that went through finished at about 21:04 GMT on 9 Nov. Failing runs began at about 20:56–21:10 GMT. So the block started at about 1 pm Pacific on 9 Nov. The app records the email as received at 19:55:55 GMT on 10 Nov, but Apple sent it at 21:10:48 GMT on 9 Nov. That is about 22 hours and 45 minutes later. So the first warning reached my inbox about a day after Apple sent it, and more pushes went out in that gap. Why was the delivery so late? Questions: The exact limit. Apple doesn't publish it. Forum posters report being blocked at about 19–20 uploads a day. Whether rejected retries extend the block. The cause of each individual failed run. Some failed for other reasons. For example, Tech build 3 failed on the macOS archive. Nothing I've found points to the app code. This is Apple's cap. From App Store Connect <no_reply@email.apple.com> Action needed: The uploaded build for ... has one or more issues. App Store Connect Hello, We noticed one or more issues with a recent delivery for the following app: App Apple ID Version 1.0 Build 5 Please correct the following issues and upload a new binary to App Store Connect. ITMS-90383: Upload limit reached - The upload limit for your account has been reached. Please wait 1 day and try again. Apple Developer Relations
Replies
1
Boosts
0
Views
95
Activity
1w